feat(delivery-promise): register pickup selector presence - #34
Conversation
Expose pickup-point-selector in the shared UI registry so consumers can detect any mounted delivery-promise block. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
2 participants
Summary (written by human)
The delivery promise related facet will only be shown in two situations
showDeliveryPromiseFacetsto trueThis PR allows the pickup-point-selector to be seen in the search-result component trough the uiRegistry. shopper-location-setter and pickup-point-selector were already in the uiRegistry
Changes
pickupPointto the sharedDeliveryPromiseContextUI registrypickup-point-selectoron mount and remove it on unmountTests
make lint: passed with no errorsAssumptions
pickup-point-selectoris optional, so its registry metadata usesrequired: falseSpec
Coordinated PR